CLCTN · BUSINESS PLAN STRESS-TEST · ANDROID · 19 SEP 2026
Most of the plan survives. The spine of it doesn't.
Nine of the eleven revenue options in the
Business Plan work on Android unchanged or better. The two that break are the two everything else was resting on:
the €24.99 one-time unlock, and
free sync you don't pay for. Both are iOS-shaped assumptions that were never labelled as such.
The useful reframing is in section 01, and it is not a monetisation question at all. Numbers here are illustrative and conservative, in the same spirit as the original — argue with the shape, not the digits.
00 · THE VERDICT, BEFORE THE DETAIL
{{ v.tag }}
{{ v.t }}
{{ v.b }}
01 · THE REFRAME THAT ANSWERS THE QUESTION
Android is not a second copy of your iOS business. Android is market B — the one section 04 of the plan already told you to build for, and then deferred because you had no way to reach it.
The plan already sorts the world into three market types: A pays for tools and hates ads, B is huge and price-sensitive and fine with ads, C finishes every deal off-platform. Look at where each one lives by device and the whole question resolves itself.
So "does the business plan work on Android" is the wrong question. The right one: does the market-B profile you already designed actually earn? Android is just the only delivery mechanism for it. And the honest answer to that is in section 05 — it earns, but not much, and never per-user.
DEVICE REALITY
{{ m.device }}
WHAT ANDROID CHANGES
{{ m.change }}
02 · EVERY REVENUE OPTION, RE-SCORED
Each line from the plan, run against a Play-store, market-B-weighted audience. Two break, two get better, the rest hold with a smaller price tag.
FROM
OPTION
ON ANDROID
WHY
{{ r.src }}
{{ r.name }}
{{ r.why }}
03 · THE TWO THINGS THAT ACTUALLY BREAK
{{ b.n }}
{{ b.t }}
{{ b.p1 }}
{{ b.p2 }}
WHAT IT COSTS
{{ b.cost }}
THE WRONG FIX
{{ b.wrong }}
04 · STORE ECONOMICS — LESS DIFFERENT THAN YOU'D THINK
The cut is a wash at your scale. The difference is entirely in who pays and what it costs to stay listed.
APP STORE
GOOGLE PLAY
CONSEQUENCE FOR THE PLAN
{{ s.k }}
{{ s.ios }}
{{ s.play }}
{{ s.note }}
05 · WHAT ANDROID WOULD REALISTICALLY MAKE
Same conservative middle case as the plan's year one, with a Play-weighted audience and the market-B profile. More than twice the installs, a fraction of the money.
SCENARIO · ANDROID YEAR ONE, MARKET-B PROFILE
{{ r.k }}
{{ r.t }}
{{ r.b }}
06 · THE REAL ARGUMENT FOR ANDROID ISN'T CONSUMER REVENUE
v3 · INSTITUTIONS · THE UNDERRATED CASE
A recyclerie doesn't get to choose what phones its volunteers own.
The plan's v3 needs staff devices — the shared shelf, roles, the lend handshake, all on a phone on a shift. In France, roughly two of every three phones in that room run Android. An iOS-only app doesn't sell a smaller institution tier; in most organisations it sells zero, because the coordinator can't run a rota on a device half the volunteers don't have.
The member side is already a link with no account and no install, so it costs nothing today. It's the staff side that is quietly iOS-gated — and v3 was named the best possible plan B.
Test it for free before writing any Kotlin: ask the recyclerie contact what the volunteers on shift carry. That is question seven, and it costs one line in an email you're already sending.
{{ s.k }}
{{ s.t }}
{{ s.b }}
07 · THE EDITS TO MAKE TO THE BUSINESS PLAN
Four, and none of them is a rewrite. Three are one sentence each; the fourth is the only one with engineering attached.
{{ e.where }}
{{ e.effort }}
08 · WHEN TO SHIP IT
{{ g.k }}
{{ g.t }}
{{ g.b }}
Companion pages:
Business Plan for the original eleven options and the three market types,
Android via Swift for how the code gets there,
Pricing by Market for the storefront price tiers. Store fee structures and Play Console policy requirements change without much notice — confirm current terms before committing a price.